FME Server is composed of a series of components, and each component is installed as a standard Windows service. There are a maximum of four services that can be associated with FME Server. The following sections describe each of the services.
This service is the main FME Server service and should always be running. By default, this service is started at system boot time.
On install, if you use the default FME Server database, it creates a service called FME Server Database, which automatically starts at system boot time. If you used your own database, such as Oracle, ensure that the service starts prior to the FME Server Service starting.
On install, if you use the default FME Server Web Application Server, the service automatically starts at system boot time. If you are using your own web application server, it is important to note that the FME Server Web Services are deployed and run by your web application server, not by FME Server itself. Ensure that your web application server is started for users to access any FME Server web services including the Web User Interfaces.
This service provides FME Server with the ability to receive email messages. By default, this service is started at boot time.
This service starts the FLEXlm License Server, which provides licenses to FME Engines. By default, this service is started at system boot time.
Starting and Stopping FME Server Manually
Although the FME Server services start automatically, you can start and stop the services manually using the standard Windows services control panel.
To access the services control panel from Windows, perform the following steps. (Other Windows operating systems have a similar procedure for accessing the services panel).
Start the FME Server service after starting the other services.
Note: You can also start and stop or restart the FME Server service manually by going to Start > Programs > FME Server > Windows Server > Start, Stop, Restart.
Determining FME Server Processes
Based on your specific environment, you might need to determine if FME Server processes are running or not. To do this, launch the Windows Task Manager and examine its process list. Ensure that the Task Manager is set to show processes from all users.
The following FME Server processes might be listed:
FMEPublisher.exe - FME Server PublicationFMERelayer.exe - FME Server Relay ManagerFMESMTPRelay.exe - FME Server Email receiverYou can install FME Server as a system service that starts when you start your system. You should do this only if you have set up system services before and understand the different run levels on your system.
Warning: Configuring scripts to run at start-up on Linux/UNIX is an advanced task. The steps for doing so vary, depending on your configuration. Use the steps listed in this section as a guide only.
FME Server is composed of a series of components, and each component has its own script. There are a few scripts that must be modified, depending on the choices you made during installation. If you performed an express installation or installed the built-in Database and Web Application Server, ensure that all scripts are moved.
To install FMEServer as a system service, you must make some changes to the init.d and rc*.d files:
and replace all occurrences of <user> with the name of the user that ran the installation of FME Server.
placing the scripts here:
Create links from the scripts you just copied to a script in the correct run level, depending on your distribution and configuration.
For Debian, this is typically 2 (rc2.d), and for Red Hat and Fedora, this is typically 5 (rc5.d). If you are unsure what run level you should use, we recommend that you contact your system administrator before proceeding.
If you are on a Debian based distribution such as Ubuntu, you can run the following commands:
update-rc.d FMEServerStart start 99 2 . stop 98 6 .
update-rc.d FMEServerAppServerStart start 99 2 . stop 99 6 .
update-rc.d FMEServerDatabaseStart start 98 2 . stop 99 6 .
update-rc.d FMEServerSMTPRelayStart start 98 2 . stop 99 6 .
On Red Hat, you can use the chkconfig command. This automatically adds them to runlevel 3. If you need to use a different run level, you need to modify the chkconfig header of these scripts, or manually:
chkconfig --add FMEServerStart
chkconfig --add FMEServerAppServerStart
chkconfig --add FMEServerDatabaseStart
chkconfig --add FMEServerSMTPRelayStart
On other distributions, or to manually set up the startup scripts, create the proper links in the appropriate run level directory.
The following steps use a run level of 2.
Create the Web Application Server startup link:
sudo ln -s /etc/init.d/FMEServerAppServerStart /etc/rc2.d/S99fmeserverappserver
Create the Database Server startup link:
sudo ln -s /etc/init.d/FMEServerDatabaseStart /etc/rc2.d/S98fmeserverdatabase
Note: It is important that this is S98, not S99.
Create the SMTP Relay startup link:
sudo ln -s /etc/init.d/FMEServerSMTPRelayStart /etc/rc2.d/S98fmeserversmtprelay
Note: It is important that this is S98, not S99.
Create the FME Server startup link:
sudo ln -s /etc/init.d/FMEServerStart /etc/rc2.d/S99fmeserver
Create the Web Application Server shutdown link:
sudo ln -s /etc/init.d/FMEServerAppServerStart /etc/rc6.d/K99fmeserverappserver
Create the Database Server shutdown link:
sudo ln -s /etc/init.d/FMEServerDatabaseStart /etc/rc6.d/K99fmeserverdatabase
Create the SMTP Relay shutdown link:
sudo ln -s /etc/init.d/FMEServerSMTPRelayStart /etc/rc2.d/K99fmeserversmtprelay
Create the FME Server shutdown link:
sudo ln -s /etc/init.d/FMEServerStart /etc/rc6.d/K98fmeserver
Note: It is important that this one is K98, not K99.
The License Server you use must be configured to start up prior to FME Server starting. If you are using the License Server provided by the FME Server install, the command to start the license server is:
<FMEServerDir>/FMEServer/Utilities/flexserver/lmgrd -c ./safe.lic -l safe.log
Starting and Stopping FME Server Manually
Although you can configure FME Server to start automatically, you can start and stop it manually by using shell scripts. To start the server, there are up to three different scripts that must be run, depending on whether you performed the express installation or installed the built-in Database and Web Application Server.
To start FME Server, run the following scripts:
Note: If the port specified during installation is a lower number than 1024, run the Application Server start-up script as the root user. Run the other scripts as the same non-root user that ran the installation of FME Server, with the exception of startFMEServerSMTPRelay.sh, which should be run as the root user.
<FMEServerDir>/Server/startApplicationServer.sh
<FMEServerDir>/Server/startDatabaseServer.sh script
<FMEServerDir>/Utilities/flexserver/lmgrd -c ./safe.lic -l safe.log
sudo <FMEServerDir>/Server startFMEServerSMTPRelay.sh
sudo sh <FMEServerDir>/Server/startServer.sh > /dev/null 2>&1 &
Note: > /dev/null 2>&1 prevents messages from outputting to the console window. These messages can still be accessed in the log file written to <FMEServerDir>/Logs. The final & runs the command in the background, returning control of the console to the user while FME Server is running.
To stop FME Server, run the following scripts:
<FMEServerDir>/Server/stopServer.sh
<FMEServerDir>/Server stopFMEServerSMTPRelay.sh
<FMEServerDir>/Server stopApplicationServer.sh
<FMEServerDir>/Server stopDatabaseServer.sh
Determining FME Server Processes
Based on your specific environment, you might need to determine if FME Server processes are running or not.
You can determine which FME Server processes are running by examining the output of:
ps -A | grep -i fme
The following FME Server processes might be listed:
FMERelayer - FME Server Relay Manager
FMESMTPRelay - FME Server Email receiver